Customers architecture #4590
Merged
Customers architecture #4590
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📦 Next.js Bundle Analysis for webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 New Pages AddedThe following pages were added to the bundle from the code in this PR:
One Hundred Sixteen Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
frankie567
commented
Dec 3, 2024
frankie567
force-pushed
the
feat/customers-1
branch
3 times, most recently
from
5841849 to
33c981f
Compare
frankie567
commented
Dec 3, 2024
| def _get_readable_customer_statement( | ||
| self, auth_subject: AuthSubject[User | Organization] | ||
| ) -> Select[tuple[Customer]]: | ||
| statement = select(Customer).where(Customer.deleted_at.is_(None)) |
There was a problem hiding this comment.
We may need to allow to list deleted customers to get historical data.
frankie567
force-pushed
the
feat/customers-1
branch
3 times, most recently
from
93ae45f to
477d2b1
Compare
frankie567
force-pushed
the
feat/customers-1
branch
4 times, most recently
from
7b5bd6a to
9752b93
Compare
frankie567
force-pushed
the
feat/customers-1
branch
from
9752b93 to
310a815
Compare
frankie567
force-pushed
the
feat/customers-1
branch
from
310a815 to
df1d8dd
Compare
frankie567
force-pushed
the
feat/customers-1
branch
from
df1d8dd to
9a3d529
Compare
frankie567
force-pushed
the
feat/customers-1
branch
from
9a3d529 to
3094c39
Compare
frankie567
force-pushed
the
feat/customers-1
branch
from
3094c39 to
8f0e091
Compare
We already have a token at hand which should be enough to prove access
…tter with User/Customer sessions
…r session from the web
…onfirmation email
Ease migration from Users. Also fixes the logic that were trying to tie a payment Transaction to a Customer/User. It was simply not working because most of the time, the Customer/User didn't exist at the time of handling the transaction. Now, we link it when handling the Order, which already had some logic to update that Transaction.
The builtin EventSource class doesn't support to pass custom headers to the request, like Authorization. From what I read, this class is somewhat deprecated and browser developers encourage to use `fetch` instead. The thing is, it's a much lower level API which doesn't do the work of reading and parsing the stream. Ref: whatwg/html#2177 I found `event-source-plus`, a library which does all that work on top of `fetch`.
…on checkout success
frankie567
force-pushed
the
feat/customers-1
branch
from
ae05ca5 to
98b2e29
Compare
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.